(96/308) 862 - gdbplugin - Breakpoints move when lines added or deleted

- **assigned_to**: nobody --> shlomy

Logged In: YES
user_id=1477607
Originator: NO

Right. I think the right solution to this is to react to buffer modifications the same way that markers do.

Regarding help: GdbPlugin is open source; if you want to contribute (e.g. by fixing this yourself) - you're more than welcome to do it. My development time of GdbPlugin is over. I only have time to support it, about 1-2 hours a week. And there's quite a lot to add to it, many little features as well as several large ones. (See TODO.txt in the root directory of the source tree for a start...)

Shlomy

Updated GdbPlugin

GdbPlugin.jar (208.0Kio)

Logged In: YES
user_id=1477607
Originator: NO

Should be fixed in SVN revision 9819. I've attached the updated GdbPlugin.jar, can you verify?
Thanks.
File Added: GdbPlugin.jar

Logged In: YES
user_id=1743859
Originator: YES

After I removed the extra directories in the GdbPlugin.jar file (see bug 1739342) the jar loads.

The breakpoint marker in the jEdit gutter moves correctly and gdb gets the new breakpoint line.

The line number in the breakpoints dockable is NOT updated.

Logged In: YES
user_id=1477607
Originator: NO

I think the breakpoints dockable should be replaced by a modal breakpoint dialog. What do you say? I don't think it makes sense for a dockable window like the breakpoints dockable to be updated whenever the line number of a breakpoint changes as result of line insertion/deletion. Would it be okay to replace the dockable with a dialog?

Logged In: YES
user_id=1743859
Originator: YES

My humble opinion: keep the breakpoints view dockable, but only update it then the user saves the file.

Logic: the file must be saved to be compiled before debugging anyway.

- **assigned_to**: shlomy --> nobody

Unassigning myself, as I no longer maintain the plugin.

- **assigned_to**: nobody --> shlomy

Unassigning myself since I no longer maintain the plugin.

- **assigned_to**: shlomy --> nobody